feat(release): add npm Package Contents Inspector#77
Merged
Conversation
Treat the packed npm tarball as a test surface: verify it ships the installer entrypoints, both bin metadata aliases, the installer shims, skills-lock.json, and every skill the lock declares — independent of any registry publish. Wire into release-pr so contents are checked before a tagged publish. Closes #52
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #52.
What
Adds
scripts/inspect_npm_package.py— a release-validation inspector that treats the packed npm tarball (npm packoutput) as the interface under test, verifying published contents independent of any registry.Checks:
bin/install.js,package.json,install.sh,install.ps1,skills-lock.jsonskills/ships payloadspackage.jsonexposes both bin entrypoints:codeforerunner,codeforerunner-installskills-lock.json(skillPath) is actually present in the tarballWired into
release-pr.ymlso contents are validated before any tagged publish.Tests (TDD)
tests/test_inspect_npm_package.py— fixture tarballs (npmpackage/prefix) drive each check; plus an end-to-end test that packs the real repo and asserts it passes (gated onnpmavailability).tests/test_workflows_yaml.py— asserts release-pr invokes the inspector.265 pytest + node suite green locally.
Out of scope
No registry publish, package-name, or auth changes (#48/#47/#46 own those).
🤖 Generated with Claude Code